All cldf data being deleted is typically a sign of an unsuccessful makecldf call - which starts by cleaning out the old cldf data.

It was a sign of me deleting the cldf-folder due to merge conflicts while working on the release candidate. I was working on a different branch and had to merge a couple of commits that were made by others directly to the master-branch instead of going through PR's, which caused several problems down the line. So we can ignore that for now because I am still preparing that release candidate and will push that through a Pull Request later today, including some last fixes.

Thank @johenglisch for catching the ID issue!

@FredericBlum Robert just made a bugfix release for pycldf. The github actions should pull in the new version automatically but you might want to upgrade pycldf in your venv to make sure pytest validates the data properly.